Skip to content

fix: readme - #22

Merged
elkaix merged 1 commit into
mainfrom
fix/readme-counter-top
Aug 14, 2026
Merged

fix: readme#22
elkaix merged 1 commit into
mainfrom
fix/readme-counter-top

Conversation

@elkaix

@elkaix elkaix commented Aug 14, 2026

Copy link
Copy Markdown
Member

Move visitor counter next to license badge in top badge row.

@elkaix
elkaix merged commit 2930936 into main Aug 14, 2026
@elkaix
elkaix deleted the fix/readme-counter-top branch August 14, 2026 06:22
@coderabbitai

coderabbitai Bot commented Aug 14, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@elkaix, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 38 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 2665858c-61a9-4f29-b49b-ea8407fc9351

📥 Commits

Reviewing files that changed from the base of the PR and between f1b3093 and 3d1a467.

📒 Files selected for processing (1)
  • README.md

Comment @coderabbitai help to get the list of available commands.

@greptile-apps

greptile-apps Bot commented Aug 14, 2026

Copy link
Copy Markdown

Greptile Summary

This update moves the README visitor counter into the primary badge row and removes the former footer copy. A source comparison and Chromium rendering check confirmed that the updated README contains one visitor badge in the leading badge paragraph and no visitor badge after the License section.

Confidence Score: 5/5

Safe to merge: the visitor counter renders in its intended location exactly once, and the removed footer copy is absent.

The README was checked against the parent revision and rendered in Chromium; the executed assertions passed for source counts, placement, and rendered DOM structure.

Files Needing Attention: None. README.md was the only changed file and its badge placement was verified.

T-Rex T-Rex Logs

What T-Rex did

  • Ran the relocation-check script to compare HEAD^ and HEAD.
  • Compared README references; HEAD^ has zero references in the top block and one after the License section, while HEAD has one reference in the leading badge block.
  • Observed Chromium render of the updated README showing a visitor image in the first badge paragraph, confirming the relocated markup displays without duplication.
  • Confirmed that no repository source files were modified and that the authored verifier and its command output were uploaded as artifacts.

View all artifacts

T-Rex Ran code and verified through T-Rex

Reviews (1): Last reviewed commit: "fix: readme" | Re-trigger Greptile

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@elkaix